fix(FOUR-32843): octane Saved Search >> When I open Saved Search, it … - #9011

…gets stuck in a "Loading" state and never displays the content.

Issue & Reproduction Steps

1. login in server https://octane-develop-qa.processmaker.net
2. Go to advanced serach https://octane-develop-qa.processmaker.net/requests/saved-searches/58762
3. Observe the request execution time and response.
4. Check the PHP worker configuration and verify that the required limits are not explicitly configured.

Solution

• • Added configurable Octane environment variables for PHP runtime limits:
  • OCTANE_MEMORY_LIMIT
  • OCTANE_MAX_EXECUTION_TIME
  • OCTANE_POST_MAX_SIZE
  • OCTANE_UPLOAD_MAX_FILESIZE
  • OCTANE_MAX_INPUT_VARS
  • OCTANE_MAX_INPUT_TIME
• Updated config/octane.php to load these values from the environment.
• Updated the Caddyfile to apply the values using FrankenPHP php_ini directives.
• Updated .env.example with the new configuration variables.
• Added the variables to the local .env configuration.
• Kept the execution-time configuration aligned between Octane and FrankenPHP.
• No application routes were added or modified for testing purposes.

How to Test

1. Configure the following values in .env:

   OCTANE_MEMORY_LIMIT=2000M
   OCTANE_MAX_EXECUTION_TIME=90
   OCTANE_POST_MAX_SIZE=200M
   OCTANE_UPLOAD_MAX_FILESIZE=200M
   OCTANE_MAX_INPUT_VARS=9000
   OCTANE_MAX_INPUT_TIME=90

2. Clear the Laravel configuration cache:

php artisan optimize:clear

3. Restart Octane completely:

php artisan octane:stop
php artisan octane:start \
  --server=frankenphp \
  --host=127.0.0.1 \
  --port=8001 \
  --max-requests=500 \
  --caddyfile=Caddyfile

4. Verify that Laravel loads the configured values:

php artisan tinker --execute="dump(config('octane.max_execution_time')); dump(config('octane.caddy.env'));"
see the savedserach
https://octane-develop-qa.processmaker.net/requests/saved-searches/58762

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-32843

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.